Road hazard communication

ABSTRACT

Apparatus, systems, and/or methods may involve reporting a road hazard. Road hazard data may be collected for an object on a road, which may include automatically generated data from a device associated with the object causing a hazard. The road hazard data may be provided to a service, an application, a device, a client, and so on. For example, the road hazard data may be merged with a map and provided to a map services client, a navigation client, and so on. An alert may be generated based on the road hazard data to warn of the hazard caused by the object. The alert may include a visual and/or audio representation of the hazard data. The alert may be used to automatically and/or manually avoid the hazard.

BACKGROUND

Embodiments generally relate to road hazard reporting. Moreparticularly, embodiments relate to communication of a road hazard(e.g., generating, collecting, and/or providing road hazard data for anobject on a road), which may be used to generate an alert to warnapproaching traffic.

A hazard platform may require user input to report a road hazard toother users. For example, the user may be required to launch anapplication and manually report a hazard, such as an accident, a parkedoff-road vehicle, and so on. Thus, the hazard platform may cause adangerous condition and/or create complexity by, for example, divertinga user's attention from the road to input data, requiring the user tostop and input the data, delaying the reporting of the hazard, relyingon user credibility, and so on. In addition, the hazard platform may notbe capable of reporting data for a moving object causing a road hazard,such as a bicycle.

BRIEF DESCRIPTION OF THE DRAWINGS

The various advantages of embodiments will become apparent to oneskilled in the art by reading the following specification and appendedclaims, and by referencing the following drawings, in which:

FIGS. 1A and 1B are block diagrams of an example approach to communicatea road hazard according to an embodiment;

FIGS. 2A and 2B are block diagrams of an example client user interfaceaccording to an embodiment;

FIG. 3 is a flowchart of an example of a method to communicate a roadhazard according to an embodiment;

FIG. 4 is a flowchart of an example of a method to communicate a roadhazard according to an embodiment;

FIG. 5 is a block diagram of an example of a logic architectureaccording to an embodiment;

FIG. 6 is a block diagram of an example of a processor according to anembodiment; and

FIG. 7 is a block diagram of an example of a system according to anembodiment.

DETAILED DESCRIPTION

FIGS. 1A and 1B show an approach to communicate a road hazard accordingto an embodiment. In the illustrated example of FIGS. 1A and 1B, two ormore objects such as vehicles 12, 14 travel in the same direction on aroad 16. The vehicles 12, 14 may include any type of vehicle such as,for example, an automobile (e.g., car, bus, etc.), a motorcycle, a truck(e.g., a cargo truck, a fire truck, pickup truck, etc.), and so on, orcombinations thereof. In addition, the road 16 may include any type ofroad such as, for example, a highway (e.g., an interstate road, a route,an expressway, etc.), a street (e.g., a city street, a town street, avillage street, etc.), and so on, or combinations thereof. The road 16may include one or more lanes such as, for example, an emergency lane ona side of the road 16 where vehicles may temporarily park, a trafficlane where vehicles may travel, a walk lane where pedestrians maytravel, and so on, or combinations thereof.

In the illustrated example of FIG. 1A, the road 16 includes a highwaywith an emergency lane 18 a and two or more travel lanes 20, 22. At timeT1, the vehicle 12 veers to a side of the road 16 and is parking in theemergency lane 18 a. Thus, the vehicle 12 causes a hazard on the road16, which may include any event, state, etc., that is hazardous and/ordangerous to traffic on the road 16. For example, the hazard may includean event by the vehicle 12 on the road 16 such as slowing to a dangerousvelocity, parking in the emergency lane 18 a, exiting the emergency lane18 a, and so on, or combinations thereof. The hazard may also include astate of the vehicle 12 on the road 16 such as being parked in theemergency lane 18 a, utilizing hazard lights, having a mechanical orelectrical failure, and so on, or combinations thereof. Thus, at timeT1, the vehicle 14 in the travel lane 20 approaches the hazard caused bythe vehicle 12.

A device associated with the vehicle 12 may report the hazard. Thedevice may be associated with the vehicle 12 using, for example, anauthentication mechanism (e.g., username, profile, encryption keys,etc.), an address (e.g., mobile internet device address, internetprotocol address, media access control address, etc.), a connection(e.g., a WiFi connection, a Bluetooth connection, a cellular connection,etc.), proximity to the vehicle 12 (e.g., located in the parked car,etc.), and so on, or combinations thereof. The device may include anycomputing device and/or data platform such as, for example, a laptop,personal digital assistant (PDA), wireless smart phone, media contentplayer, imaging device, mobile Internet device (MID), any smart devicesuch as a smart phone, smart tablet, smart TV, wearable computer, and soon, or any combination thereof. In one example, the device may include amobile computing device of a vehicle user such as, for example, a smartphone of a driver of the vehicle 12, of a passenger in the vehicle 12,and so on, or combinations thereof. In another example, the device mayinclude any on-board computing system integral with and/or mechanicallyremovable from the vehicle 12 such as, for example, an in-vehicleinfotainment (IVI) system, a navigation system, a vehicle computersystem, and so on, or combinations thereof.

The device associated with the vehicle 12 may include a display, anoutput to a display, and so on, or combinations thereof. For example,the device associated with the vehicle 12 may include a touch screen, aliquid crystal display (LCD), a light emitting diode (LED) display, aprojection display, and so on, or combinations thereof. The deviceassociated with the vehicle 12 may also include an output to the displaysuch as a windshield display, a mirror display, an eye glass display,and so on, or combinations thereof. In addition, the display may includea two-dimensional (2D) display, a three-dimensional (3D) display, and soon, or combinations thereof. In one example, the display may be used tomanually input data related to a hazard setting (e.g., continuallyreport hazard data, etc.), to manually input the road hazard data, andso on, or combinations thereof. In addition, the device may include anaudio component such as a microphone to, for example, verbally inputdata. Moreover, the device associated with the vehicle 12 may include aninput from an audio component, such as a microphone of the vehicle 12.

The device associated with the vehicle 12 may automatically generateand/or provide road hazard data for the vehicle 12. The road hazard datamay include accelerometer data (e.g., velocity, acceleration,deceleration, etc.), gyroscope data (e.g., movement, elevation, etc.),global positioning data (e.g., global position, location on the road,etc.), and so on, or combinations thereof. In one example, theacceleration data may be used to indicate a dangerous speed of thevehicle 12, a trajectory toward the emergency lane 18 a, etc., thegyroscope data may be used to indicate a parked state, an angled state(e.g., being towed, changing tire, etc.), etc., the global positioningdata may be used to indicate the position of the vehicle 12 on the road16, and so on, or combinations thereof. The road hazard data may alsoinclude hazard feature data for the vehicle 12. For example, the hazardfeature data may include data indicating that hazard lights of thevehicle 12 are utilized (initiated, operated, etc.), data indicatingthat a turn signal of the vehicle 12 is utilized, data indicating that acheck engine light of the vehicle 12 is utilized, and so on, orcombinations thereof.

The device associated with the vehicle 12 may generate the road hazarddata using a local component. For example, the device associated withthe vehicle 12 (e.g., a mobile computing device, an IVI system, anavigation system, a vehicle computer system, etc.) may utilize a localdevice processor, memory, storage, global positioning system (GPS), andso on, or combinations thereof. In addition, the device associated withthe vehicle 12 may utilize a component of another system associated withthe vehicle 12 to generate the road hazard data. For example, a mobilecomputing device associated with the vehicle 12 may interact with avehicle computer system to utilize an on-board vehicle processor,memory, storage, GPS, and so on, or combinations thereof. Thus, forexample, the mobile computing device associated with the vehicle 12 mayutilize a local GPS and an on-board vehicle processor or memory toobtain acceleration data, deceleration data, vehicle speed data, vehiclestopped state data, vehicle elevation state data, vehicle location data,hazard lights utilization data, mechanical or electrical failure data,and so on, or combinations thereof.

In the illustrated example of FIG. 1A, the device associated with thevehicle 12 may provide the road hazard data to a hazard server 24 attime T2. The device associated with the vehicle 12 may be registeredwith the hazard server 24, and/or may forward the road hazard data tothe server 24 using, for example, an authentication mechanism (e.g.,username, profile, encryption keys, etc.), an address (e.g., mobileinternet device address, internet protocol address, media access controladdress, etc.), a connection (e.g., a WiFi connection, a Bluetoothconnection, a cellular connection, etc.), proximity to the vehicle 12(e.g., in the parked car, etc.), and so on, or combinations thereof.Thus, the hazard server 24 may receive and/or collect data that may beautomatically generated from the device associated with the vehicle 12.

The road hazard data may be stored in any physical or virtual locationof the hazard server 24 such as, for example, server memory, cache, harddrive, database, table, library, and so on, or combinations thereof. Theroad hazard data may be stored in the same server, may be distributedacross two or more servers in the same or different physical and/orvirtual location, and so on, or combinations thereof. Thus, the hazardserver 24 may include a cloud-computing server.

The hazard server 24 may include an interface to provide the road hazarddata and/or an alert based on the road hazard data. In one example, theinterface may include an application programming interface (API) toallow access to the road hazard data from, for example, a service, anapplication, a device, and so on, or combinations thereof. The API mayallow for any type of access to the road hazard data and/or alert, suchas push access (e.g., via a real-time update, periodic scheduled update,etc.), pull access (e.g., via real-time requests, periodic scheduledrequests, etc.), and so on, or combinations thereof. In the illustratedexample of FIG. 1A, a service 26 may access the road hazard data tointegrate the road hazard data with a service, an application, a device,and so on, or combinations thereof. For example, the service 26 mayinclude Google maps, Telemap, NavNGo, iGo, etc., which may provide a mapservice and/or a navigation service to be used by a client userinterface (e.g., a client application, a client device, etc.). Thus, theservice 26 may merge the accessed road hazard data with a map to provideadditional capabilities for the map service and/or the navigationservice such as, for example, to provide (e.g., transmit) a hazard alertincluding hazard detail (e.g., hazard summary, etc.). At time T3 in theillustrated example, the service 26 may access the road hazard data viathe API of the hazard server 24 and merge the road hazard data with themap service and/or the navigation service that it provides to generate amap with an alert based on the road hazard data (e.g., a drop pin forthe hazard on the map, etc.).

The hazard server 24 may also include a network interface to provide(e.g., transmit) the road hazard data and/or the alert directly to aclient user interface (e.g., a client application, a client device,etc.), with or without the API of the hazard server 24. The networkinterface may allow for any type of access to the road hazard dataand/or the alert, such as push access (e.g., via a real-time update,periodic scheduled update, etc.), pull access (e.g., via real-timerequests, periodic scheduled requests, etc.), and so on, or combinationsthereof. In one example, the hazard server 24 may provide a service suchas tow-truck service (e.g., to tow vehicles), a law enforcement service(e.g., to respond to emergencies), a traffic warning service (e.g., tonotify the public of hazardous events), a map service (e.g., to providea map), a navigation service (e.g., to provide a navigation path), andso on, or combinations thereof. Thus, the hazard server 24 may integratethe road hazard data with the service, an application, and/or a deviceto directly provide the road hazard data and/or the alert to a clientuser interface of a client (e.g., a map client, etc.).

For example, the hazard server 24 may utilize an API of the service 26to access a library to add capabilities to the service provided by thehazard server 24. Thus, the hazard server 24 may access a map libraryvia the API of the service 26 (e.g., a map service) and merge theaccessed data (e.g., the map) with the road hazard data to generate thealert (e.g., on the map) based on the road hazard data. In anotherexample, the hazard server 24 may include a database of maps to createthe map merged with the road hazard data and to generate the alert onthe map based on the road hazard data. The hazard server 24 may alsoprovide, for example, navigation data for a navigation service such asnavigation paths, text-to-speech route data, traffic patterns, and soon, or combinations thereof. Thus, the map provided to a map client mayincorporate navigation services in response to user input. At time T3 inthe illustrated example, the hazard server 24 may integrate the roadhazard data with a map service and/or a navigation service to generate amap with an alert based on the road hazard data (e.g., a drop pin forthe hazard on the map, etc.).

The alert may include any visual representation and/or audiorepresentation of the road hazard data. For example, the alert mayinclude a point generated on a map to indicate a location of the hazard,a point generated on a map having a property to indicate a type ofhazard (e.g., a specific color of the point to indicate parking), apoint generated on a map having a property to indicate a type of objectcausing the hazard (e.g., a truck shape for a truck, etc.), a pointgenerated on the map including hazard details (e.g., via an automaticpop-up window, a selectable pop-up window, etc.), a drop pin generatedon the map, and so on, or combinations thereof. The alert may include anicon generated on a map such as, for example, an image associated withthe object. The image may include a picture of the vehicle 12, a pictureof the user associated with the vehicle 12 (e.g., a profile picture ofthe driver, of the passenger, etc.), a logo indicating a type of object(e.g., make of a vehicle, etc.), and so on, or combinations thereof.

The alert may be rendered independent of a map. For example, the alertmay include a written summary of the event on a display having hazarddetails such as the object causing hazard, the distance to the hazard,and so on, or combinations thereof. The alert may be presented toapproaching objects without a map using, for example, an electronicmessage board on a road, a text message application, and so on, orcombinations thereof. In addition, the alert may be presented by aplurality of displays. For example, the alert may be simultaneouslypresented by a display of an IVI system, a navigation system, a smartphone, and so on. In one example, a display of an IVI system may renderthe alert on a map merged with the hazard while a display of a smartphone renders the alert via a text message. The alert may include audiodata, such as a text-to-speech message, a chime sound, and so on, orcombinations thereof. The alert may include a standalone alert, and/ormay be simultaneously rendered with other alerts. Thus, an audio alertmay be simultaneously rendered with a visual alert, another audio alert,and so on, or conations thereof.

At time T4, the hazard server 24 and/or the service 26 may provide theroad hazard data to a device associated with the vehicle 14. Forexample, a map merged with the road hazard data may be provided to thedevice associated with the vehicle 14, an alert including hazard detailsindependently of a map may be provided to the device associated with thevehicle 14, and so on. In another example, the service 26 may provide amap and the hazard server 24 may provide the road hazard data, thealert, and so on, or combinations thereof. Thus, the device associatedwith the vehicle 14 may include any computing device and/or dataplatform such as, for example, the same type of computing device and/ordata platform associated with the vehicle 12. The device may include,for example, a mobile computing device of a vehicle user such as, forexample, a smart phone of a driver of the vehicle 14, of a passenger inthe vehicle 14, and so on, or combinations thereof. In another example,the device may include any on-board computing system which is integralwith and/or mechanically removable from the vehicle 14 such as, forexample, an in-vehicle infotainment (IVI) system, a navigation system,and so on, or combinations thereof.

Accordingly, the device associated with the vehicle 12 and the deviceassociated with the vehicle 14 may be the same or different type ofdevice including the same or different capabilities (e.g., audio/videofunctionality, hazard reporting, alert rendering, etc.). The device maybe associated with the vehicle 14 using, for example, an authenticationmechanism (e.g., username, profile, encryption keys, etc.), an address(e.g., mobile internet device address, internet protocol address, mediaaccess control address, etc.), a connection (e.g., a WiFi connection, aBluetooth connection, a cellular connection, etc.), proximity to thevehicle 14 (e.g., in the parked car, etc.), and so on, or combinationsthereof. In addition, the device associated with the vehicle 14 mayreceive the road hazard data from the hazard server 24 and/or theservice 26 using, for example, an authentication mechanism, aconnection, proximity to the vehicle 14, and so on, or combinationsthereof.

Proximity between the vehicles 12, 14 may be utilized to implement adesired geographic and/or temporal scope for the road hazard data, thealert, and so on, or combinations thereof. In one example, the deviceassociated with vehicle 12 may generate and provide the road hazard datawithin a predetermine time from the hazard event (e.g., start, end,etc.), the hazard server 24 may broadcast the road hazard data and/orthe alert to any device within a predetermined distance to the vehicle12, and/or the device associated with the vehicle 14 may render the roadhazard data within a predetermined time based on, for example, velocityof the vehicle 14 and distance to the vehicle 12. In another example,the vehicle 14 may render the alert for a region of interest based on,for example, a navigation path selected by the user, a region selectedby the user on a map, and so on, or combinations thereof. The settingsto generate, provide, and/or render data may be accessed via a userinterface such as, for example, a service user interface to configure asetting for the hazard server 24 and/or the service 26, a client userinterface to configure a setting for the devices associated with thevehicles 12, 14 (or other devices), and so on, or combinations thereof.

The device associated with the vehicle 14 may include a display torender the road hazard data, the map integral with the road hazard data,the alert, navigation data, and so on, or combinations thereof. Forexample, the device associated with the vehicle 14 may render the roadhazard data via a touch screen, an LCD, a LED display, a projectiondisplay, and so on, or combinations thereof. The device associated withthe vehicle 14 may also include an output to the display such as awindshield display, a mirror display, an eye glass display, and so on,or combinations thereof. In addition, the display may include a 2Ddisplay, a 3D display, and so on, or combinations thereof. The deviceassociated with the vehicle 14 may include an audio component, such as aspeaker to render the alert in an audio representation. In addition, thedevice associated with the vehicle 14 may include an output to an audiocomponent, such as a speaker of the vehicle 14.

The display may be used to manually input data related to a hazardsetting such as, for example, to continually receive road hazard data,to receive road hazard data on request, to exclude/include objects(e.g., ignore parked cars when on street, focus on cyclists and notpedestrians when on street, etc.), to set a preference to receive alerts(e.g., based on time such as 5 minutes away, based on distance such as 5miles away, ignore all, etc.) and so on, or combinations thereof. Itshould be understood that one or more settings may be automatically setand/or applied, for example based on current location, velocity,boundaries between types of roads, history analytics, and so on, orcombinations thereof. In one example, a setting to include cyclists andexclude parked cars may be automatically applied based on historyanalytics when a vehicle crosses from a highway boundary to a streetboundary. Moreover, it should be understood that a display used torender the alert may not be in direct relationship with the vehicle 14.For example, the display may include an electronic display located onthe road 16 (e.g., electronic billboard display, etc.), a display of adevice used to plan a trip or utilize a service not currently located inthe vehicle 14, a display of another approaching vehicle, and so on, orcombinations thereof.

The alert may cause the vehicle 14 to manually avoid the hazard causedby the vehicle 12 at time T5. For example, the driver of the vehicle 14may view and/or hear the alert and manually switch the vehicle 14 fromthe lane 20 to the lane 22. In another example, the driver of thevehicle 14 may view and/or hear the alert and manually switch thevehicle 14 to an alternative path off of the road 16, which may bedetermined using on a map service, a navigation service, and so on, orcombinations thereof. In addition, the alert may cause the vehicle 14 toautomatically avoid the hazard caused by the vehicle 12 at time T5. Forexample, the device associated with the vehicle 12 may automaticallyswitch the vehicle 14 from the lane 20 to the lane 22 when the vehicle12 is controlled by a computer system, may automatically switch the pathof the vehicle 14 to an alternative path off of the road 16, and so on,or combinations thereof.

Additionally, respective devices associated with the vehicles 12, 14 mayinclude (and/or communicate with) any other components to communicate ahazard on the road 16. For example, the devices associated with thevehicles 12, 14 may include an image capture device to capture imagedata, wherein the image capture device may include a front-facingcamera, a rear-facing camera, a 2D camera, a 3D camera, a night-visioncamera, and so on, or combinations thereof. The captured image data maybe utilized in an element recognition processes such as, for example,scale invariant feature transform (SIFT), compressed histogram ofgradients (CHoG) descriptor, and so on, or combinations thereof. Thus,for example, a pair-wise element-matching process may match a queryimage against a database image to recognize an element (e.g., object,feature, landscape, etc.) in an image (e.g., a video, a frame of avideo, a photograph, etc.). The process may include, for example,performing a pair-wise comparison on a short list of candidates mostlikely to match the query image.

Indexing of image elements may include known processes such as, forexample, using approximate nearest neighbor search of SIFT descriptorswith a best-bin-first strategy, a BoF model using a BoF codebookconstructed by a K-means clustering of a training set of descriptors,using a codebook constructed including a hierarchical k-means clusteringto create a vocabulary tree (VT), using a locally-sensitive hashingprocess, using any other tree-based processes, and so on. A geometricverification process may also be used to analyze the image data. Forexample, element location information in a query image and a databaseimage may be used to confirm that element matches are consistent with achange in view point between the two images. Any known process may beused to perform geometric verification. For example, a regressionprocess such as random sample consensus may be used, checks based onfeature-orientation information may be used, re-ranking before theregression process may be used, and so on.

The element recognition process may be implemented at any location suchas, for example, at the location of the vehicle 12, at the location ofthe vehicle 14, at the location of the hazard server 24, and so on, orcombinations thereof. In one example, a pairwise comparison may beimplemented by the hazard server 24 utilizing image data received and alocal database of images, a database of images accessible to the hazardserver 24 e.g., via an image service or an image server, and so on, orcombinations thereof. The result of the comparison may be provided bythe hazard server 24. In another example, a pairwise comparison may beimplemented by the vehicle 12 and/or the vehicle 14 utilizing capturedimage data and a local database of images, a database of imagesaccessible to the vehicles 12, 14 e.g., via an image service or an imageserver, and so on, or combinations thereof. The result of the pairwisecomparison may be provided by the vehicles 12, 14.

In a further example, the front-facing camera and/or the rear-facingcamera of the vehicles 12, 14 may capture image data to be used torecognize one or more elements of the road 16 such as, for example, alane divider between the emergency lane 18 a and the travel lane 20. Inaddition, the front-facing camera and/or the rear-facing camera of thevehicles 12, 14 may capture image data to be used to recognize one ormore elements indicating a hazard event such as, for example, veeringtoward a guard rail, veering toward a pre-defined landscape (e.g.,trees, bushes, etc.). Moreover, the front-facing camera and/or therear-facing camera of the vehicles 12, 14 may capture image data to beused to recognize one or more elements indicating a hazard state suchas, for example, where an image includes a relatively static opticalflow when the vehicle 12 is parked, where an image is tilted when thevehicle 12 is being towed or during a tire change, and so on.

Thus, for example, the front-facing camera and/or the rear-facing cameraof the vehicles 12 may provide image data used in an element recognitionprocess to recognize a lane divider and a guard rail to indicate thatthe vehicle 12 is veering across a lane divider toward a guard rail attime T1, while the front-facing camera of the vehicle 14 may provideimage data used in an element recognition process to recognize thevehicle 12 and the lane divider to indicate that the vehicle 12 isveering across the lane divider towards the emergency lane 18 a at timeT1. Accordingly, elements (e.g., objects, features, landscapes, etc.) inthe field of view of the front-facing camera and/or the rear-facingcamera of the vehicles 12, 14 may be used to generate and/or provideroad hazard data.

In another example, image recognition of a tow truck may indicate ahazard, image recognition of a flare may indicate a hazard, imagerecognition of an emergency responder (e.g., vehicle such as a policevehicle, person such as a fireman, etc.) may indicate a hazard, and soon, or combinations thereof. Thus, a device associated with an objectcausing a road hazard may report the hazard by generating and/orproviding road hazard data (e.g., including the image data), a deviceassociated with oncoming traffic may report the hazard by generatingand/or providing the road hazard data (e.g., including the image data),and so on, or combinations thereof. It should be understood that otherdevices (e.g., a camera on a road, a camera on an aircraft, a speedcamera, a satellite camera, etc.) may be used alone, or in combinationwith a device associated with an object causing the hazard and/or adevice associated with oncoming traffic to provide the road hazard data.It should also be understood that any pre-defined event and/or state maybe reported automatically to alert and/or notify of users about ahazard.

In the illustrated example of FIG. 1B, the road 16 includes a streetwith a sidewalk 18 b and two or more travel lanes 20, 22. At time T1, amoving object such as a bicycle 28 in the lane 20 causes a hazard on theroad 16, which may include any event, state, etc. that is hazardousand/or dangerous to traffic on the road 16. For example, the hazard mayinclude an event caused by the bicycle 28 such as cycling in the lane20, crossing the lane 20, and so on, or combinations thereof. The hazardmay also include a state of the bicycle 28 such as being stationary inthe lane 20, being positioned in the travel lane 20, and so on. Thus, attime T1, the vehicle 14 in the travel lane 20 approaches the hazardcaused by the vehicle 12.

A device associated with the bicycle 28 may report the hazard. Thedevice may be associated with the bicycle 28 using, for example, anauthentication mechanism (e.g., username, profile, encryption keys,etc.), an address (e.g., mobile internet device address, internetprotocol address, media access control address, etc.), a connection(e.g., a WiFi connection, a Bluetooth connection, a cellular connection,etc.), proximity to the bicycle 28 (e.g., on a bicycle, etc.), and soon, or combinations thereof. The device may include any computing deviceand/or data platform, such as, for example, a laptop, personal digitalassistant (PDA), wireless smart phone, media content player, imagingdevice, mobile Internet device (MID), any smart device such as a smartphone, smart tablet, smart TV, wearable computer, and so on, or anycombination thereof. Thus, the device may include a mobile computingdevice (e.g., smart phone) of a cyclist 30 riding the bicycle 28. Inanother example, the device may include any on-board computing systemwhich is integral with and/or mechanically removable from the bicycle 28such as, for example, an in-vehicle infotainment (IVI) system, anavigation system, a bicycle computer system, and so on, or combinationsthereof. Thus, the computing device may include a display, an audiocomponent, an image capture device, and so on, or combinations thereof.

The device associated with the bicycle 28 may automatically generate andprovide the road hazard data for the bicycle 28. In one example, theroad hazard data may include accelerometer data, gyroscope data, globalpositioning data, image data, and so on, or combinations thereof. Itshould be understood that the road hazard data (e.g. including imagedata) may also be generated and/or provided by a device associated withthe vehicle 14, alone or in combination with the road hazard data (e.g.including image data) provided by the device associated with the bicycle28. For example, a front-facing camera of the vehicle 14 may captureimage data to be used in an element recognition process to recognize thebicycle 28 and/or the cyclist 30, wherein the image data and/or a resultof a pair-wise comparison may be generated and/or provided to the hazardserver 24. In addition, the road hazard data may be continually providedto the hazard server 24. Thus, at time T2 in the illustrated example ofFIG. 1B, the road hazard data indicating that the bicycle 28 is in thetravel lane 20 may be provided to the hazard server 24. In response tothe road hazard data a map merged with the road hazard data, and/or analert, may be provided at time T3 by the hazard server 24 and/or theservice 26.

Thus, for example, the hazard server 24 and/or the service 26 mayprovide (e.g., transmit) the road hazard data to the device associatedwith the bicycle 28 at time T4 as a map merged with the road hazarddata, as an alert including hazard details for the road hazard dataindependently of the map, and so on, or combinations thereof. Moreover,the alert may cause the approaching vehicle 14 to manually avoid themoving hazard and/or automatically avoid the moving hazard at time T5.Thus, the vehicle 14 may move from the lane 20 to the lane 22 at time T5to avoid the hazard caused by the bicycle 28 and/or the cyclist 30. Itshould be understood that repeated alerts may be generated to notify ofa change in approaching hazards caused by a moving object such as thebicycle 28, wherein the approaching vehicle 14 may continually updatethe action taken to avoid the hazard.

Turning now to FIGS. 2A and 2B, a client user interface 202 is shownaccording to an embodiment. The client user interface 202 may include aclient application, a client device (e.g., a mobile computing device, anIVI system, a navigation system, an on-board computer system, etc.), andso on, or combinations thereof. In the illustrated example, the clientuser interface 202 includes a display 232 to render navigation data 234.In the illustrated example of FIGS. 2A to 2B, navigation data 234includes a standard view map showing topography proximate to an object's(e.g., a vehicle, etc.) position that is associated with the client userinterface 232. The map rendered on the display 232 via the client userinterface 202 may include any view, such as a satellite view, a hybridstandard-satellite view, and so on, or combinations thereof. Inaddition, the map rendered on the display 232 via the client userinterface 202 may include any region of interest, such as an entirenavigation path of interest to a user, a portion thereof, and so on.

In the illustrated example, the navigation data 234 also includes thename of the road the object is traveling (e.g., “Road Name”), thecurrent local time (e.g., “Time”), the speed the object is traveling(e.g. “Speed”), the distance remaining before the path of the objectshould change (e.g., “Distance), the direction that the object shouldchange once the distance is reached (e.g., arrow), and the speed limitof the road (e.g., the integer 60). The settings for the navigation data234 may be provided by a main menu of the user client interface 202,which may include options to set map views, type of data to bedisplayed, the units of the data to be displayed (e.g., miles, meters,etc.), the color of the elements on the map, the brightness of thedisplay, day settings, night settings, text-to-speech language settings,and so on, or combinations thereof.

The illustrated client user interface 202 also includes a hazard menu236, which may be accessed from the main menu. The hazard menu 236 mayprovide any setting related to road hazard data and/or alerts based onthe road hazard data. For example, the hazard menu 236 includes a roadsetting tab 238 to define road hazard data to be generated, received,and/or rendered for a particular the type of road being traveled. Thus,the road setting tab 238 may include an option to, for example, generateand receive road hazard data for parking vehicles when traveling on ahighway, exclude generating or receiving road hazard data for parkedvehicle when traveling on a street, include generating and receivingroad hazard data for bicycles when traveling on a street, and so on, orcombinations thereof. The hazard menu 236 also includes an objectsetting tab 240 to define road hazard data to be generated, received,and/or rendered for a particular the type of object on the road. Forexample, the object setting 240 may include an option to generate andreceive road hazard data for a particular type of vehicle, such as for acar, and to exclude generating or receive road hazard data for anotherparticular type of vehicle, such as a motorcycle.

The hazard menu 236 also includes an alert setting tab 242 to define analert to be generated, received, and/or rendered based on the roadhazard data. For example, the alert setting tab 242 may include anoption to generate an alert for a parking vehicle and not for a parkedvehicle, an option to receive an alert for a bicycle in the road and notfor a bicycle crossing the road, and so on, or combinations thereof. Inaddition, the alert setting tab 242 may define a representation for analert to be generated, received, and/or rendered. For example, the alertsetting tab 242 may include an option to generate and/or render a visualalert, such as a visual alert 244 illustrated in FIG. 1A and/or a visualalert 246 illustrated in FIG. 1B. The alert setting tab may also includeoption to, for example, define the properties of the visual alert (e.g.,appearance, size, color, content, icons, images, window features such asautomatic pop-up window or selectable pop-up window, etc.), choose apreset profile (e.g., highway profile, street profile, etc.), and so on,or combinations thereof.

The alert setting tab 242 may also include an option to generate and/orrender an audio alert, such as a text-to-speech alert, a chime (e.g.,custom sound, preset sound, etc.), and so on, or combinations thereof.The alert setting tab 242 may also include an option to define theoutput device of the alert, such as a speaker of the client userinterface 202, a speaker of a vehicle, a speaker of a device associatedwith the vehicle (e.g., smart phone, etc.), and so on, or combinationsthereof. In the illustrated examples of FIGS. 2A to 2B, the visualalerts 244, 246 may be rendered on the display 232 via the client userinterface 202, which is associated with a vehicle where the client userinterface 202 resides. While not shown, it should be understood that thehazard menu 236 may include any other setting to generate, receive,and/or render road hazard data such as, for example, image capturesettings. In one example, an image capture setting may be used tospecify whether to use a camera, to specify which camera to use, tospecify the conditions to use the camera, to specify night-visionfunctionality, and so on, or combinations thereof.

In one example, the visual alert 244 may be rendered at the vehicle 14illustrated in FIG. 1A when the client user interface 202 is associatedwith the vehicle 14. The illustrated visual alert 244 includes hazarddetails, such as a description of the hazard, the distance to thehazard, and so on. An accompanying audio alert such as a chime or atext-to-speech reciting the description of the hazard in visual alert244 may also be rendered via the client user interface 202. Thus, thedisplay 232 of the client user interface 202 may render the visual alert244 (e.g., a parking car 500 meters away) and cause the hazard to beavoided by the vehicle 14. In the illustrated example of FIG. 2B, avisual alert 246 may be rendered at the vehicle 14 illustrated in FIG.1B when the client user interface 202 is associated with the vehicle 14.The illustrated visual alert 246 includes hazard details, such as adescription of the hazard, the distance to the hazard, and so on. Anaccompanying audio alert such as a chime or a text-to-speech recitingthe description of the hazard in visual alert 246 may also be renderedvia the client user interface 202. Thus, the display 232 of the clientuser interface 202 may render the visual alert 246 (e.g., a cyclist 500meters away) and cause the hazard to be avoided by the vehicle 14.

FIG. 3 shows a method 302 to communicate a road hazard according to anembodiment. The method 302 may be implemented as a set of logicinstructions and/or firmware stored in a machine- or computer-readablestorage medium such as random access memory (RAM), read only memory(ROM), programmable ROM (PROM), flash memory, etc., in configurablelogic such as, for example, programmable logic arrays (PLAs), fieldprogrammable gate arrays (FPGAs), complex programmable logic devices(CPLDs), in fixed-functionality logic hardware using circuit technologysuch as, for example, application specific integrated circuit (ASIC),CMOS or transistor-transistor logic (TTL) technology, or any combinationthereof. For example, computer program code to carry out operationsshown in the method 302 may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. Moreover, the method 302 may be implemented using any of theherein mentioned circuit technologies.

Illustrated processing block 350 involves collecting road hazard datafor an object on a road. The object on the road may include a vehicle,such as an automobile, a motorcycle, a truck, a bicycle, a pedestrian,and so on, or combinations thereof. In addition, the road may include ahighway having one or more lanes such as, for example, an emergencylane, a travel lane, and so on, to combinations thereof. The road mayinclude a street having one or more lanes such as, for example, a walklane, a travel lane, and so on, or combinations thereof. The hazardcaused by the object may include any event, state, etc., that ishazardous and/or dangerous to traffic on the road, such as slowing to adangerous velocity, parking in the emergency lane of the road, cyclingin the travel lane of the road, and so on, or combinations thereof. Theroad hazard data may include, for example, accelerometer data, gyroscopedata, global positioning data, hazard feature data, image data, and soon, or combinations thereof.

The processing block 350 involves collecting automatically generateddata from a device associated with the object causing the hazard. Itshould be understood that the method 302 may include data collected thatis not automatically generated (e.g., manually generated) and/or that isautomatically generated by a device not associated with the objectcausing the hazard. For example, the road hazard data may include dataautomatically generated and/or provided by an image capture device onthe road (e.g., a speed camera, etc.), by a device associated with anobject (e.g., a vehicle) approaching the hazard, and so on, orcombinations thereof. The device generating the road hazard data mayinclude any computing device and/or data platform, such as a laptop,personal digital assistant (PDA), wireless smart phone, media contentplayer, imaging device, mobile Internet device (MID), any smart devicesuch as a smart phone, smart tablet, smart TV, wearable computer, and soon, or combinations thereof. The device may also include any on-boardcomputing system integral with and/or mechanically removable from theobject such as, for example, an in-vehicle infotainment (IVI) system, anavigation system, a vehicle computer system, a bicycle computer system,and so on, or combinations thereof.

The device may render a generation setting to set, for example, the typeof road hazard data to generate, the road hazard data to provide, and soon, or combinations thereof. The device may include a display (and/oroutput to a display) to input the road hazard data, such as a 2Ddisplay, a 3D display, a windshield display, an eye glass display, atouch screen display, a LCD, a LED display and so on, or combinationsthereof. In addition, the device may include an audio component, such asa speaker, a microphone to input data, and so on, or combinationsthereof. Moreover, the device may include an image capture device tocapture image data, wherein the image capture device may include, forexample, a front-facing camera, a rear-facing camera, a 2D camera, a 3Dcamera, a night-vision camera, and so on, or combinations thereof.

In one example, the object causing the hazard may include a vehicle at aside of a highway and/or a bicycle in a traveling lane of a street,wherein the road hazard data may include object position data and/or thedevice may include a mobile computing device of an object user (e.g.,vehicle driver, etc.). Thus, the device associated with the objectcausing the hazard on the road may capture image data (e.g., a video, aframe of a video, a picture, etc.), may determine a position of theobject, and/or may determine a utilization of a hazard feature of theobject, such as a location on the road, utilization of hazard lights,and so on, or combinations thereof.

The device may provide the road hazard data to a server, which mayinclude a cloud-computing server. In one example, the cloud-computingserver may be a part of a plurality of connected computers through acommunication network and may engage in distributed computing over thenetwork In one example, the server may engage in distributed computingto run a program, an application, etc., on various connected computersat the same time. In another example, the server may engage indistributed computing to provide network-based services over physicalserver hardware, virtual hardware, and so on, or combinations thereof.Thus, the server may collect the road hazard data, wherein the roadhazard data may include automatically generated data from a deviceassociated with the object causing the hazard, from a device associatedwith an approaching object (e.g., to the hazard, etc.), from a deviceindependent of the device causing the hazard and/or the oncoming object,and so on, or combinations thereof.

Illustrated block 351 involves providing the road hazard data, whereinan alert may be generated based on the road hazard data to warn of ahazard caused by the object. In one example, a server collecting theroad hazard data may include an application programming interface (API)to allow a service (e.g., a map service) to access the road hazard dataand integrate the road hazard data with a service, an application, adevice, and so on, or combinations thereof. For example, a map servicemay merge the road hazard data with a map, wherein an alert based on theroad hazard data may appear on the map to warn an approaching objectuser (e.g., approaching vehicle driver, etc.) of the hazard.

In another example, the server may include a network interface toprovide the road hazard data directly to a client user interface, withor without the API. For example, the server may provide a service suchas tow-truck service, a law enforcement service, a traffic warningservice, a map service, a navigation service, and so on, or combinationsthereof. Thus, for example, the server may merge the road hazard datawith a map and provide the map to the client user interface for a mapservice (e.g., to a map client), a navigation service (e.g., to anavigation client), and so on, or combinations thereof. In addition, theserver may generate the alert based on the road hazard data, wherein thealert may appear on the map to warn an approaching object user (e.g.approaching vehicle driver, etc.) of the hazard.

The alert may include any visual representation and/or audiorepresentation of the road hazard data, such as a point generated on themap, a window generated on the map, a drop pin generated on the map, anicon generated on the map and so on, or combinations thereof. Inaddition, the alert may include a message to be displayed, independentof the map, including hazard details such as a written summary of theevent, written distance to the hazard, and so on, or combinationsthereof. The alert may also include audio data, such as a text-to-speechmessage, a chime sound, and so on, or combinations thereof.

The server and/or the service may provide the road hazard data to adevice associated with an approaching object such as, for example, avehicle approaching the hazard, a vehicle approaching the object thatcaused the hazard, and so on, or combinations thereof. The device may bethe same or different type of device (e.g., a mobile device, an integralIVI device, etc.) with the same or different capabilities (e.g.,audio/video functionality, hazard reporting, alert rendering, etc.) asthe device that reported the hazard. The device may render a map mergedwith the road hazard data, navigation data, and so on, or combinationsthereof. In addition, device may render the alert.

The device may render an alert setting, such as a road setting, anobject setting, an alert setting, and so on, or combinations thereof. Inone example, the device may include a display (and/or output to adisplay) to present the alert, such as a 2D display, a 3D display, awindshield display, an eye glass display, a touch screen display, a LCD,a LED display and so on, or combinations thereof. In addition, thedevice may include an audio component, such as a speaker to render thealert, a microphone to input data, and so on, or combinations thereof.Moreover, the device may include an image capture device to captureimage data, wherein the image capture device may include, for example, afront-facing camera, a rear-facing camera, a 2D camera, a 3D camera, anight-vision camera, and so on, or combinations thereof.

The alert may cause the approaching object to manually avoid the hazardcaused by the object. For example, a driver of an approaching vehiclemay view and/or hear the alert and manually switch the lane of thevehicle. In another example, the driver of the approaching vehicle mayview and/or hear the alert and manually switch the path of the vehicleoff of the road, which may be determined based on a map service, anavigation service, and so on, or combinations thereof. In addition, thealert may cause the object to automatically avoid the hazard. Forexample, a device associated with a vehicle (e.g., an IVI system, anon-board vehicle computer system) may automatically switch the lane ofthe vehicle when a computer controls the vehicle.

Turning now to FIG. 4 , a method 402 to communicate a road hazard isshown according to an embodiment. The method 402 may be implementedusing any of the herein mentioned technologies. Thus, the method 402 maybe implemented as a set of logic instructions and/or firmware stored ina machine- or computer-readable storage medium, and so on. Illustratedprocessing block 452 determines a position of an object. In one example,the position of the object may be determined using global positioningsystem (GPS) data. A determination may be made at block 453 as towhether the object is at a side of a road. For example, the object maybe veering toward a side of a road, may be crossing into an emergencylane of a road, may be exiting an emergency lane of a road, and so on.If so, processing block 454 determines a utilization of a hazard featureof the object, such as utilization of hazard lights, and so on. Thus,road hazard data such as the location of the object and the utilizationof hazard features may be automatically generated.

If the object is not at a side of the road, the method 402 may returnback to the processing block 452 to determine a position of the sameobject, another object, and so on, or combinations thereof. Adetermination may be made at block 455 as to whether the object is in atravel lane. If not, the method 402 may return back to the processingblock 452 to determine a position of the same object, another object,and so on, or combinations thereof. If the object is in the travel laneof the road, a determination may be made at block 456 as to whether theobject is a bicycle, a cyclist, and so on. If not, the processing block454 may determine a utilization of a feature hazard since the object mayinclude, for example, a broken down car in the travel lane of the roadthat is utilizing hazard lights. If the object is in the travel lane andis a cyclist, road hazard data automatically generated that indicatesthe location of the object, the type of object, etc., may be provided.In the illustrated example of FIG. 4 , processing block 457automatically provides the automatically generated road hazard data(e.g., the position data, the feature utilization data, etc.).

Processing block 458 collects the road hazard data for the object on theroad. For example, the road hazard data may be stored in memory, in ahard drive, in a library, in a table, and so on, or combinationsthereof. Processing block 459 provides access to the road hazard data,which may be in any format such as, for example, raw hazard data, hazarddata integrated with a map, an alert representing the hazard data, andso on, or combinations thereof. For example, the processing block 459may involve an application programming interface (API) to provide accessto the road hazard data, a network interface to provide access to theroad hazard data, and so on, or combinations thereof.

A determination may be made at block 460 as to whether a service isdirectly provided, such as a map service. If not, processing block 461provides the road hazard data and/or the alert to a service, such as amap service, a navigation service, a traffic service, etc. The servicemay integrate the road hazard data with an application, a device, etc.,and provide the road hazard data to a client application, a clientdevice, and so on, or combinations thereof. If a service is to bedirectly provided, the road hazard data may be directly integrated withthe service. For example, the road hazard data may be merged with a mapfor a map service, a navigation service, and so on, or combinationsthereof. Thus, processing block 462 may provide the road hazard data,the alert, and/or a map (e.g., for a map service) merged with the roadhazard data to a client application, a client device, etc. of a client(e.g., map client, navigation client, etc.).

Processing block 463 renders the map merged with the road hazard dataand other data, such as navigation data. For example, a client userinterface may be used to display the map merged with the road hazarddata and the navigation data. Processing block 464 provides forrendering the alert to the user. For example, the alert may be renderedon the map. The alert may also be rendered independently of the map, forexample by using an audio alert, by presenting the alert on a display,by presenting the alert without the map, and so on. In addition,processing block 465 provides for taking evasive action in response tothe alert. For example, the evasive action may include manually changinga lane of approaching traffic to avoid the hazard, automaticallychanging a navigation path of approaching traffic to avoid the hazard,and so on, or combinations thereof.

FIG. 5 shows an apparatus 502 including logic 566 to communicate a roadhazard according to an embodiment. The logic architecture 566 may begenerally incorporated into a platform such as such as a laptop,personal digital assistant (PDA), wireless smart phone, media player,imaging device, mobile Internet device (MID), any smart device such as asmart phone, smart tablet, smart TV, computer server, wearable computer,in-vehicle infotainment (IVI) system, navigation system, vehiclecomputer system, bicycle computer system, server, and so on, orcombinations thereof. The logic architecture 566 may be implemented inan application, operating system, media framework, hardware component,and so on, or combinations thereof. For example, the logic architecture566 may be implemented in a processor, such as a central processing unit(CPU), a graphical processing unit (GPU), a visual processing unit(VPU), a sensor, an operating system, an application, and so on, orcombinations thereof. The apparatus 502 may include and/or interact withstorage 590, applications 592, memory 594, display 596, CPU 598, and soon, or combinations thereof.

In the illustrated example, the logic architecture 566 includes a datacollector module 567 to collect road hazard data for an object on aroad. In one example, the road hazard data may include automaticallygenerated and/or provided data from a device associated with the object.The object on the road may include a vehicle, such as an automobile, amotorcycle, a truck, a bicycle, pedestrians, and so on, or combinationsthereof. In addition, the road may include a highway including anemergency lane, a travel lane, and so on, to combinations thereof. Theroad may also include a street including a walk lane, a travel lane, andso on, or combinations thereof.

The hazard caused by the object may include any event, state, etc., thatis hazardous and/or dangerous to traffic on the road (e.g., vehicles,drivers, passengers, pedestrians, etc.), such as slowing to a dangerousvelocity, parking in the emergency lane of the road, cycling in thetravel lane of the road, and so on, or combinations thereof. The datacollector module 567 may collect road hazard data including, forexample, accelerometer data, gyroscope data, global positioning data,hazard feature data, image data, and so on, or combinations thereof. Thedata collector module 567 may, for example, store the road hazard datain the storage 590, the memory 594, off-platform memory, and so on, orcombinations thereof.

The logic architecture 566 includes an interface module 568 to providethe road hazard data. In the illustrated example, the interface module568 includes an application programming interface (API) module 569 toallow, for example, a service (e.g., a map service) to access the roadhazard data and integrate the road hazard data with a service, anapplication, a device, and so on, or combinations thereof. For example,a map service may merge the road hazard data with a map, wherein analert based on the road hazard data may appear on the map to warn anapproaching object user (e.g., approaching vehicle driver, etc.) of thehazard. The interface module 568 may also include a network interfacemodule 570 to provide (e.g., transmit) the road hazard data with orwithout the API module 569. The network interface module 570 may providea wide variety of communication functionality, such as cellulartelephone (e.g., W-CDMA (UMTS), CDMA2000 (IS-856/IS-2000), etc.), WiFi,Bluetooth (e.g., IEEE 802.15.1-2005, Wireless Personal Area Networks),WiMax (e.g., IEEE 802.16-2004), Global Positioning Systems (GPS), spreadspectrum (e.g., 900 MHz), and other radio frequency (RF) telephonypurposes.

The logic architecture 566 includes a hazard service module 571, whichmay provide a service to a client. The illustrated hazard service module571 includes an image recognition module 572 to recognize an element ofan image. In one example, the image recognition module 572 may implementan element recognition process (e.g., pair-wise comparison, etc.) torecognize an element (e.g., object, feature, landscape, etc.) of animage including, for example, a video, a frame of a video, a photograph,and so on, or combinations thereof. The hazard service module 571 alsoincludes a map service module 573 to merge the road hazard data with amap. For example, the map service module 573 may merge the road hazarddata from the memory 594 with a map from the storage 590, and providethe map to the client user interface via the network interface module570 for a map service, a navigation service, and so on. In anotherexample, the map service module 573 may utilize the network interfacemodule 570 to obtain the map to merge the map with the road hazard data.

The hazard service module 571 also incudes a service alert module 574 togenerate an alert based on the road hazard data, wherein the alert mayappear on the map to warn an object (e.g., approaching traffic, vehicledriver, vehicle passenger, service user, etc.) of the hazard. The alertmay include any visual representation and/or audio representation of theroad hazard data, such as point on the map, an icon on the map, a textmessage, a text-to-speech message, a chime, and so on, or combinationsthereof. In addition, the hazard service module 571 includes a serviceuser interface module 575 to provide a service setting. The service userinterface module 575 may provide any desired interface, such as agraphical user interface, a command line interface, and so on, orcombinations thereof. The service user interface module 575 may provideaccess to one or more settings associated with road hazard data, such asoptions to define service type (e.g., map service, etc.), scope of roadhazard data (e.g., temporal scope, geographic scope, etc.), clientregistration (e.g., security, proximity to object, etc.), and so on, orcombinations thereof. In one example, the service user interface module575 utilizes the display 596 to render the service setting.

The logic architecture 566 includes a hazard reporter module 576 togenerate and/or provide the road hazard data. The illustrated hazardreporter module 576 includes an image capture module 577 to captureimage data. In one example, the image capture module 577 may captureimage data including, for example, a video, a frame of a video, aphotograph, and so on, or combinations thereof. The captured image datamay be used to recognize an element of an image. For example, the imagerecognition module 572 may use the captured image data to recognize anelement in a frame of a video. The hazard reporter module 575 includes aposition module 578 to determine a position (or any other data relatedto movement) of the object causing the hazard. For example, the positionmodule 578 may utilize a sensor (e.g., an accelerometer, a gyroscope, aglobal positioning system, etc.) to determine accelerometer data,gyroscope data, global positioning data, and so on. The hazard reportermodule 575 also includes a hazard feature module 579 to determine autilization of a hazard feature of the object. For example, the hazardfeature module 579 may utilize the CPU 598 to determine whether hazardlights are utilized, signal lights are utilized, warning lights areutilized (e.g., check engine, etc.) and so on, or combinations thereof.In one example, the hazard reporter module 576 may communicate the roadhazard data to the data collector module 567.

The logic architecture 566 includes a client module 580 to render data.The client module 580 includes a client map module 581 to render the mapmerged with the road hazard data, navigation data, and so on, orcombinations thereof. In one example, the client map module 581 mayutilize the display 596 to render the map. The client module 580 alsoincudes a client alert module 582 to render the alert, for example fromthe service alert module 574. In one example, the client alert module582 may utilize the display 596 to render the alert, an audio componentto render the alert, and so on, or combinations thereof. In addition,the client module 580 includes a client user interface module 583 torender a client setting, such as a road setting, an object setting, analert setting, an image capture setting, and so on, or combinationsthereof. The client user interface module 583 may provide any desiredinterface, such as a graphical user interface, a command line interface,and so on, or combinations thereof. In one example, the client userinterface module 583 may utilize the display 596 to render a clientsetting.

The logic architecture 566 includes an action module 584 to provideevasive action. For example, the action module 584 may cause anapproaching object (e.g., approaching traffic, an approaching vehicle,etc.) to automatically avoid the hazard in response to the alert. In oneexample, the action module 584 may utilize the CPU 598 to change a laneof the approaching object. In another example, the action module 584 mayutilize a global positioning system and the CPU 598 to automaticallyswitch and a navigation path of the approaching object. In a furtherexample, the action module 584 may utilize the GPS and the display 596to render the new path to cause a driver of the approaching object tomanually change the lane of the approaching object, and so on. Thus, itshould be understood that generating and/or providing the road hazarddata may itself operate as an alert without audio and/or visualrepresentation. For example, the receipt of generated road hazard dataat the approaching object may be utilized without user awareness (e.g.,without a visual alert, an audio alert, etc.) to avoid the hazard.

While examples have shown separate modules for illustration purposes, itis should be understood that one or more of the modules of the logicarchitecture 566 may be implemented in one or more combined modules,such as a single module including the map service module 573 and theservice alert module 574 used to generate a map with merged road hazarddata and alerts. In another example, a single module may include one ormore of the data collector module 567, the interface module 568, thehazard service module 571, the hazard reporter module 576, the clientmodule 580, and the action module 584. In addition, it should beunderstood that one or more logic components of the apparatus 566 may beon platform, off platform, and/or reside in the same or different realand/or virtual space as the apparatus 502. For example, the datacollector module 567 may reside in a cloud-computing environment on aserver while one or more of the other modules of the logic architecture566 may reside on a computing platform where a user is physicallylocated, and vice versa, or combinations thereof.

Turning now to FIG. 6 , a processor core 200 according to one embodimentis shown. The processor core 200 may be the core for any type ofprocessor, such as a micro-processor, an embedded processor, a digitalsignal processor (DSP), a network processor, or other device to executecode to implement the technologies described herein. Although only oneprocessor core 200 is illustrated in FIG. 6 , a processing element mayalternatively include more than one of the processor core 200illustrated in FIG. 6 . The processor core 200 may be a single-threadedcore or, for at least one embodiment, the processor core 200 may bemultithreaded in that it may include more than one hardware threadcontext (or “logical processor”) per core.

FIG. 6 also illustrates a memory 270 coupled to the processor 200. Thememory 270 may be any of a wide variety of memories (including variouslayers of memory hierarchy) as are known or otherwise available to thoseof skill in the art. The memory 270 may include one or more code 213instruction(s) to be executed by the processor 200 core, wherein thecode 213 may implement the logic architecture 566 (FIG. 5 ), alreadydiscussed. The processor core 200 follows a program sequence ofinstructions indicated by the code 213. Each instruction may enter afront end portion 210 and be processed by one or more decoders 220. Thedecoder 220 may generate as its output a micro operation such as a fixedwidth micro operation in a predefined format, or may generate otherinstructions, microinstructions, or control signals which reflect theoriginal code instruction. The illustrated front end 210 also includesregister renaming logic 225 and scheduling logic 230, which generallyallocate resources and queue the operation corresponding to the convertinstruction for execution.

The processor 200 is shown including execution logic 250 having a set ofexecution units 255-1 through 255-N. Some embodiments may include anumber of execution units dedicated to specific functions or sets offunctions. Other embodiments may include only one execution unit or oneexecution unit that may perform a particular function. The illustratedexecution logic 250 performs the operations specified by codeinstructions.

After completion of execution of the operations specified by the codeinstructions, back end logic 260 retires the instructions of the code213. In one embodiment, the processor 200 allows out of order executionbut requires in order retirement of instructions. Retirement logic 265may take a variety of forms as known to those of skill in the art (e.g.,re-order buffers or the like). In this manner, the processor core 200 istransformed during execution of the code 213, at least in terms of theoutput generated by the decoder, the hardware registers and tablesutilized by the register renaming logic 225, and any registers (notshown) modified by the execution logic 250.

Although not illustrated in FIG. 6 , a processing element may includeother elements on chip with the processor core 200. For example, aprocessing element may include memory control logic along with theprocessor core 200. The processing element may include I/O control logicand/or may include I/O control logic integrated with memory controllogic. The processing element may also include one or more caches.

FIG. 7 shows a block diagram of a system 1000 in accordance with anembodiment. Shown in FIG. 7 is a multiprocessor system 1000 thatincludes a first processing element 1070 and a second processing element1080. While two processing elements 1070 and 1080 are shown, it is to beunderstood that an embodiment of system 1000 may also include only onesuch processing element.

System 1000 is illustrated as a point-to-point interconnect system,wherein the first processing element 1070 and second processing element1080 are coupled via a point-to-point interconnect 1050. It should beunderstood that any or all of the interconnects illustrated in FIG. 7may be implemented as a multi-drop bus rather than point-to-pointinterconnect.

As shown in FIG. 7 , each of processing elements 1070 and 1080 may bemulticore processors, including first and second processor cores (i.e.,processor cores 1074 a and 1074 b and processor cores 1084 a and 1084b). Such cores 1074, 1074 b, 1084 a, 1084 b may be configured to executeinstruction code in a manner similar to that discussed above inconnection with FIG. 6 .

Each processing element 1070, 1080 may include at least one shared cache1896. The shared cache 1896 a, 1896 b may store data (e.g.,instructions) that are utilized by one or more components of theprocessor, such as the cores 1074 a, 1074 b and 1084 a, 1084 b,respectively. For example, the shared cache may locally cache datastored in a memory 1032, 1034 for faster access by components of theprocessor. In one or more embodiments, the shared cache may include oneor more mid-level caches, such as level 2 (L2), level 3 (L3), level 4(L4), or other levels of cache, a last level cache (LLC), and/orcombinations thereof.

While shown with only two processing elements 1070, 1080, it is to beunderstood that the scope is not so limited. In other embodiments, oneor more additional processing elements may be present in a givenprocessor. Alternatively, one or more of processing elements 1070, 1080may be an element other than a processor, such as an accelerator or afield programmable gate array. For example, additional processingelement(s) may include additional processors(s) that are the same as afirst processor 1070, additional processor(s) that are heterogeneous orasymmetric to processor a first processor 1070, accelerators (such as,e.g., graphics accelerators or digital signal processing (DSP) units),field programmable gate arrays, or any other processing element. Theremay be a variety of differences between the processing elements 1070,1080 in terms of a spectrum of metrics of merit including architectural,microarchitectural, thermal, power consumption characteristics, and thelike. These differences may effectively manifest themselves as asymmetryand heterogeneity amongst the processing elements 1070, 1080. For atleast one embodiment, the various processing elements 1070, 1080 mayreside in the same die package.

First processing element 1070 may further include memory controllerlogic (MC) 1072 and point-to-point (P-P) interfaces 1076 and 1078.Similarly, second processing element 1080 may include a MC 1082 and P-Pinterfaces 1086 and 1088. As shown in FIG. 7 , MC's 1072 and 1082 couplethe processors to respective memories, namely a memory 1032 and a memory1034, which may be portions of main memory locally attached to therespective processors. While the MC logic 1072 and 1082 is illustratedas integrated into the processing elements 1070, 1080, for alternativeembodiments the MC logic may be discrete logic outside the processingelements 1070, 1080 rather than integrated therein.

The first processing element 1070 and the second processing element 1080may be coupled to an I/O subsystem 1090 via P-P interconnects 1076, 1086and 1084, respectively. As shown in FIG. 10 , the I/O subsystem 1090includes P-P interfaces 1094 and 1098. Furthermore, I/O subsystem 1090includes an interface 1092 to couple I/O subsystem 1090 with a highperformance graphics engine 1038. In one embodiment, bus 1049 may beused to couple graphics engine 1038 to I/O subsystem 1090. Alternately,a point-to-point interconnect 1039 may couple these components.

In turn, I/O subsystem 1090 may be coupled to a first bus 1016 via aninterface 1096. In one embodiment, the first bus 1016 may be aPeripheral Component Interconnect (PCI) bus, or a bus such as a PCIExpress bus or another third generation I/O interconnect bus, althoughthe scope is not so limited.

As shown in FIG. 7 , various I/O devices 1014 such as the display 232(FIGS. 2A and 2B) and/or the display 596 (FIG. 5 ) may be coupled to thefirst bus 1016, along with a bus bridge 1018 which may couple the firstbus 1016 to a second bus 1020. In one embodiment, the second bus 1020may be a low pin count (LPC) bus. Various devices may be coupled to thesecond bus 1020 including, for example, a keyboard/mouse 1012,communication device(s) 1026 (which may in turn be in communication witha computer network), and a data storage unit 1019 such as a disk driveor other mass storage device which may include code 1030, in oneembodiment. The code 1030 may include instructions for performingembodiments of one or more of the methods described above. Thus, theillustrated code 1030 may implement the logic architecture 566 (FIG. 5), already discussed. Further, an audio I/O 1024 may be coupled tosecond bus 1020.

Note that other embodiments are contemplated. For example, instead ofthe point-to-point architecture of FIG. 7 , a system may implement amulti-drop bus or another such communication topology. Also, theelements of FIG. 7 may alternatively be partitioned using more or fewerintegrated chips than shown in FIG. 7 .

Thus, embodiments may report on-road and/or off-road dangerous eventssuch as, for example, a car stopping by the side of the road via adevice associated with the car (e.g., an IVI system, a smart phone,etc.). For example, the IVI system may report the position (e.g.,location) and/or status (e.g., parked, utilizing hazard lights) to aserver (e.g., cloud-computing server, etc.), wherein the information maybe accessed and integrated with applications, services, devices, etc. toautomatically alert cars approaching in the same direction. The alertmay be utilized to automatically and/or manually avoid the hazard causedby the car. Accordingly, there may be no need to divert a driver'sattention from the road to report the event, the event may be reportedautomatically to even a first approaching driver, and so on.

In addition, on-road dangerous events caused by moving objects, such asa cyclist, may be reported to approaching traffic that will encounterthe moving object to avoid the hazard (e.g., even if dark, may divertthe car to another path, change lanes, etc.). Moreover, it should beunderstood that any object causing a hazard on a road and capable ofgenerating or providing road hazard data, such as a pedestrian having asmart phone and walking in the road, may automatically report thedangerous event to allow approaching traffic to avoid and/or prepare forthe hazard (e.g., slow down).

ADDITIONAL NOTES AND EXAMPLES

Examples may include subject matter such as a method, means forperforming acts of the method, at least one machine-readable mediumincluding instructions that, when performed by a machine cause themachine to performs acts of the method, or an apparatus or system tocommunicate a road hazard according to embodiments and examplesdescribed herein.

Example 1 may include an apparatus having a data collector module tocollect road hazard data for an object on a road, wherein the roadhazard data is to include automatically generated data from a deviceassociated with the object. The apparatus may include an interfacemodule to provide the road hazard data, wherein an alert is to begenerated based on the road hazard data to warn of a hazard by theobject.

Example 2 may include the subject matter of Example 1 and furtheroptionally may include, wherein the object is to include one or more ofa vehicle at a side of a highway or a bicycle in a traveling lane of astreet, wherein the road hazard data is to include object position data,and wherein the device is to include a mobile computing device of anobject user.

Example 3 may include the subject matter of any of Example 1 to Example2 and further optionally may include, wherein the device is to furtherinclude a hazard reporter module, the hazard reporter module includingone or more of an image capture module to capture image data to be usedto recognize an element of an image, a position module to determine aposition of the object, or a hazard feature module to determine autilization of a hazard feature of the object.

Example 4 may include the subject matter of any of Example 1 to Example3 and further optionally may include, wherein the device is to furtherinclude a client module, the client module including one or more of aclient map module to render a map merged with the road hazard data andnavigation data, a client alert module to render the alert to a user ora client setting module to render an alert setting.

Example 5 may include the subject matter of any of Example 1 to Example4 and further optionally may include a hazard service module, the hazardservice module including one or more of an image recognition module torecognize an element of an image, a map service module to merge the roadhazard data with a map, or a service alert module to generate the alertbased on the road hazard data, wherein the alert is to appear on the mapto warn at least approaching traffic of the hazard.

Example 6 may include the subject matter of any of Example 1 to Example5 and further optionally may include, wherein the interface module is toinclude an application programming interface to allow a map servicemodule to access the road hazard data to merge the road hazard data witha map, wherein the alert is to appear on the map to warn an approachingobject user of the hazard.

Example 7 may include the subject matter of any of Example 1 to Example6 and further optionally may include a display to render the alert, thedisplay including one or more of a windshield display, an eye glassdisplay, a touch screen display, a liquid crystal display, or a lightemitting diode display.

Example 8 may include the subject matter of any of Example 1 to Example7 and further optionally may include the alert is to cause anapproaching object to one or more of manually avoid the hazard andautomatically avoid the hazard.

Example 9 may include at least one computer-readable medium comprisingone or more instructions that when executed on a computing device causethe computing device to collect road hazard data for an object on aroad, wherein the road hazard data is to include automatically generateddata from a device associated with the object, or provide the roadhazard data, wherein an alert is to be generated based on the roadhazard data to warn of a hazard by the object.

Example 10 may include the subject matter of Example 9 and furtheroptionally may include, wherein the object is to include one or more ofa vehicle at a side of a highway or a bicycle in a traveling lane of astreet, wherein the road hazard data is to include object position data,and wherein the device is to include a mobile computing device of anobject user.

Example 11 may include the subject matter of any of Example 9 to Example10 and further optionally may include to capture image data to be usedto recognize an element of an image, determine a position of the object,and determine a utilization of a hazard feature of the object.

Example 12 may include the subject matter of any of Example 9 to Example11 and further optionally may include to render a map merged with theroad hazard data and navigation data, render the alert to a user, andrender an alert setting.

Example 13 may include the subject matter of any of Example 9 to Example12 and further optionally may include to recognize an element of animage, merge the road hazard data with a map, and generate the alertbased on the road hazard data, wherein the alert is to appear on the mapto warn an approaching object user of the hazard.

Example 14 may include the subject matter of any of Example 9 to Example12 and further optionally may include to provide an applicationprogramming interface to allow a map service to access the road hazarddata to integrate the road hazard data with a map, wherein the alert isto appear on the map to warn at least approaching traffic of the hazard.

Example 15 may include the subject matter of any of Example 9 to Example14 and further optionally may include to render the alert on a display.

Example 16 may include the subject matter of any of Example 9 to Example15 and further optionally may include to one of more of manually avoidthe hazard or automatically avoid the hazard.

Example 17 may include a method to communicate a road hazard, comprisingcollecting road hazard data for an object on a road, wherein the roadhazard data includes automatically generated data from a deviceassociated with the object, and providing the road hazard data, whereinan alert is to be generated based on the road hazard data to warn of ahazard by the object.

Example 18 may include the subject matter of Example 17 and furtheroptionally may include, wherein the object includes one or more of avehicle at a side of a highway or a bicycle in a traveling lane of astreet, wherein the road hazard data includes object position data, andwherein the device includes a mobile computing device of an object user.

Example 19 may include the subject matter of any of Example 17 toExample 18 and further optionally may include capturing image data usedto recognize an element of an image, determining a position of theobject, and/or determining a utilization of a hazard feature of theobject.

Example 20 may include the subject matter of any of Example 17 toExample 19 and further optionally may include rendering a map mergedwith the hazard data and navigation data, rendering the alert to a user,and/or rendering an alert setting.

Example 21 may include the subject matter of any of Example 17 toExample 22 and further optionally may include recognizing an element ofan image, merging the road hazard data with a map, and/or generating thealert based on the hazard data, wherein the alert appears on the map towarn an approaching object user of the hazard.

Example 22 may include the subject matter of any of Example 17 toExample 23 and further optionally may include providing an applicationprogramming interface to allow a map service to access the road hazarddata to merge the road hazard data with a map, wherein the alert appearson the map to warn at least approaching traffic of the hazard.

Example 23 may include the subject matter of any of Example 17 toExample 24 and further optionally may include rendering the alert on adisplay.

Example 24 may include the subject matter of any of Example 17 toExample 25 and further optionally may include manually avoiding thehazard, and/or automatically avoiding the hazard.

Example 25 may include at least one computer-readable medium includingone or more instructions that when executed on one or more computingdevices causes the one or more computing devices to perform the methodof any of Example 17 to Example 24.

Example 26 may include an apparatus including means for performing themethod of any of Example 17 to Example 24.

Various embodiments may be implemented using hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude processors, microprocessors, circuits, circuit elements (e.g.,transistors, resistors, capacitors, inductors, and so forth), integratedcircuits, application specific integrated circuits (ASIC), programmablelogic devices (PLD), digital signal processors (DSP), field programmablegate array (FPGA), logic gates, registers, semiconductor device, chips,microchips, chip sets, and so forth. Examples of software may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor.

Embodiments are applicable for use with all types of semiconductorintegrated circuit (“IC”) chips. Examples of these IC chips include butare not limited to processors, controllers, chipset components,programmable logic arrays (PLAs), memory chips, network chips, and thelike. In addition, in some of the drawings, signal conductor lines arerepresented with lines. Some may be different, to indicate moreconstituent signal paths, have a number label, to indicate a number ofconstituent signal paths, and/or have arrows at one or more ends, toindicate primary information flow direction. This, however, should notbe construed in a limiting manner. Rather, such added detail may be usedin connection with one or more exemplary embodiments to facilitateeasier understanding of a circuit. Any represented signal lines, whetheror not having additional information, may actually comprise one or moresignals that may travel in multiple directions and may be implementedwith any suitable type of signal scheme, e.g., digital or analog linesimplemented with differential pairs, optical fiber lines, and/orsingle-ended lines.

Example sizes/models/values/ranges may have been given, althoughembodiments are not limited to the same. As manufacturing techniques(e.g., photolithography) mature over time, it is expected that devicesof smaller size could be manufactured. In addition, well knownpower/ground connections to IC chips and other components may or may notbe shown within the figures, for simplicity of illustration anddiscussion, and so as not to obscure certain aspects of the embodiments.Further, arrangements may be shown in block diagram form in order toavoid obscuring embodiments, and also in view of the fact that specificswith respect to implementation of such block diagram arrangements arehighly dependent upon the platform within which the embodiment is to beimplemented, i.e., such specifics should be well within purview of oneskilled in the art. Where specific details (e.g., circuits) are setforth in order to describe example embodiments, it should be apparent toone skilled in the art that embodiments may be practiced without, orwith variation of, these specific details. The description is thus to beregarded as illustrative instead of limiting.

Some embodiments may be implemented, for example, using a machine ortangible computer-readable medium or article which may store aninstruction or a set of instructions that, if executed by a machine, maycause the machine to perform a method and/or operations in accordancewith the embodiments. Such a machine may include, for example, anysuitable processing platform, computing platform, computing device,processing device, computing system, processing system, computer,processor, or the like, and may be implemented using any suitablecombination of hardware and/or software. The machine-readable medium orarticle may include, for example, any suitable type of memory unit,memory device, memory article, memory medium, storage device, storagearticle, storage medium and/or storage unit, for example, memory,removable or non-removable media, erasable or non-erasable media,writeable or re-writeable media, digital or analog media, hard disk,floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact DiskRecordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk,magnetic media, magneto-optical media, removable memory cards or disks,various types of Digital Versatile Disk (DVD), a tape, a cassette, orthe like. The instructions may include any suitable type of code, suchas source code, compiled code, interpreted code, executable code, staticcode, dynamic code, encrypted code, and the like, implemented using anysuitable high-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language.

Unless specifically stated otherwise, it may be appreciated that termssuch as “processing,” “computing,” “calculating,” “determining,” or thelike, refer to the action and/or processes of a computer or computingsystem, or similar electronic computing device, that manipulates and/ortransforms data represented as physical quantities (e.g., electronic)within the computing system's registers and/or memories into other datasimilarly represented as physical quantities within the computingsystem's memories, registers or other such information storage,transmission or display devices. The embodiments are not limited in thiscontext.

The term “coupled” may be used herein to refer to any type ofrelationship, direct or indirect, between the components in question,and may apply to electrical, mechanical, fluid, optical,electromagnetic, electromechanical or other connections. In addition,the terms “first”, “second”, etc. may be used herein only to facilitatediscussion, and carry no particular temporal or chronologicalsignificance unless otherwise indicated. Additionally, it is understoodthat the indefinite articles “a” or “an” carry the meaning of “one ormore” or “at least one”. In addition, as used in this application and inthe claims, a list of items joined by the terms “one or more of” and “atleast one of” can mean any combination of the listed terms. For example,the phrases “one or more of A, B or C” can mean A; B; C; A and B; A andC; B and C; or A, B and C.

Those skilled in the art will appreciate from the foregoing descriptionthat the broad techniques of the embodiments may be implemented in avariety of forms. Therefore, while the embodiments have been describedin connection with particular examples thereof, the true scope of theembodiments should not be so limited since other modifications willbecome apparent to the skilled practitioner upon a study of thedrawings, the specification, and following claims.

What is claimed is:
 1. A first computing device of a first vehicle,comprising: network interface circuitry configured to communicateinformation to a second computing device of a second vehicle; and one ormore processors configured to: identify hazard information indicative ofone or more road hazards detected by the first vehicle, the hazardinformation indicating that the first vehicle represents a hazard toother vehicles sharing an environment with the first vehicle; andtransmit an alert message to the second computing device of the secondvehicle, the alert message being indicative of the one or more roadhazards, wherein the second vehicle is capable of presenting the alertmessage based upon a distance between the one or more road hazards andthe second vehicle.
 2. The first computing device of claim 1, whereinthe hazard information is indicative of vehicle hazard warning lights.3. The first computing device of claim 1, wherein the alert message istransmitted to the second computing device during a time intervalcomprising a time elapsed from when the hazard information indicative ofthe one or more road hazards was identified.
 4. The first computingdevice of claim 1, wherein the hazard information is indicative of thefirst vehicle slowing to a predetermined speed.
 5. The first computingdevice of claim 1, wherein the hazard information is indicative of thefirst vehicle being at a predetermined type of a road location.
 6. Thefirst computing device of claim 1, wherein the hazard information isindicative of the first vehicle having a mechanical failure.
 7. Thefirst computing device of claim 1, wherein the first computing device isintegrated as part of the first vehicle.
 8. A non-transitorycomputer-readable medium that includes machine-readable instructionsthat, when executed by a first computing device of a first vehicle,cause the first computing device to: identify hazard informationindicative of one or more road hazards detected by the first vehicle,the hazard information indicating that the first vehicle represents ahazard to other vehicles sharing an environment with the first vehicle;and transmit an alert message to a second computing device of a secondvehicle, the alert message being indicative of the one or more roadhazards, wherein the second vehicle is capable of presenting the alertmessage based upon a distance between the one or more road hazards andthe second vehicle.
 9. The non-transitory computer-readable medium ofclaim 8, wherein the hazard information is indicative of vehicle hazardwarning lights.
 10. The non-transitory computer-readable medium of claim8, wherein the alert message is transmitted to the second computingdevice during a time interval comprising a time elapsed from when thehazard information indicative of the one or more road hazards wasidentified.
 11. The non-transitory computer-readable medium of claim 8,wherein the hazard information is indicative of the first vehicleslowing to a predetermined speed.
 12. The non-transitorycomputer-readable medium of claim 8, wherein the hazard information isindicative of the first vehicle being at a predetermined type of a roadlocation.
 13. The non-transitory computer-readable medium of claim 8,wherein the hazard information is indicative of the first vehicle havinga mechanical failure.
 14. A first computing device of a first vehicle,comprising: network interface circuitry configured to receiveinformation from a second computing device of a second vehicle; and oneor more processors configured to: receive hazard information indicativeof one or more road hazards detected by the second vehicle, the hazardinformation indicating that the second vehicle represents a hazard toother vehicles sharing an environment with the first vehicle; receive analert message from the second computing device of the second vehicle,the alert message being indicative of the one or more road hazards andbeing selectively presented at the first vehicle based upon a distancebetween the one or more road hazards and the first vehicle.
 15. Thefirst computing device of claim 14, wherein the hazard informationincludes information indicative of the second vehicle using hazardwarning lights.
 16. The first computing device of claim 14, wherein thealert message is received from the second computing device during a timeinterval comprising a time elapsed from when the hazard informationindicative of the one or more road hazards was identified.
 17. The firstcomputing device of claim 14, wherein the hazard information isindicative of the second vehicle slowing to a predetermined speed. 18.The first computing device of claim 14, wherein the hazard informationis indicative of the second vehicle being at a predetermined type of aroad location.
 19. The first computing device of claim 14, wherein thehazard information is indicative of the second vehicle having amechanical failure.
 20. The first computing device of claim 14, whereinthe first computing device is integrated as part of the first vehicle.21. A non-transitory computer-readable medium that includesmachine-readable instructions that, when executed by a first computingdevice of a first vehicle, cause the first computing device to: receivehazard information indicative of one or more road hazards detected by asecond vehicle, the hazard information indicating that the secondvehicle represents a hazard to other vehicles sharing an environmentwith the first vehicle; and receive an alert message from a secondcomputing device of the second vehicle, the alert message beingindicative of the one or more road hazards and being selectivelypresented at the first vehicle based upon a distance between the one ormore road hazards and the first vehicle.
 22. The non-transitorycomputer-readable medium of claim 21, wherein the hazard information isindicative of vehicle hazard warning lights used by the second vehicle.23. The non-transitory computer-readable medium of claim 21, wherein thealert message is received from the second computing device during a timeinterval comprising a time elapsed from when the hazard informationindicative of the one or more road hazards was identified.
 24. Thenon-transitory computer-readable medium of claim 21, wherein the hazardinformation is indicative of the second vehicle slowing to apredetermined speed.
 25. The non-transitory computer-readable medium ofclaim 21, wherein the hazard information is indicative of the secondvehicle being at a predetermined type of a road location.
 26. Thenon-transitory computer-readable medium of claim 21, wherein the hazardinformation is indicative of the second vehicle having a mechanicalfailure.